Deploying JD Edwards EnterpriseOne On Premises on Microsoft Windows

You can orchestrate a Deployment Plan using Advanced mode, which allows you to:

• Modify and add servers to an existing Orchestration that was created using the Quick Start wizard.
  
• Create a new Orchestration with no guidance from a wizard. Unlike using the Quick Start wizard, the Advanced mode will not guide you through the required sequence of machines to satisfy dependencies of the configuration. For example, the allowable pathcodes for an Enterprise Server are dependent on the schemas previously selected for the Database Server.

The required sequence of adding instances to an orchestration and the rules related to the machines and pathcodes is as follows:

1. Database Server

   You can create five database instances if you select one schema per instance.

2. Enterprise Server

   One to many Enterprise Servers can be created. At least one Enterprise Server must be created with selected pathcodes available from the available schemas that were selected for the Database Server. An Enterprise Server must be configured before you can add HTML Servers. If multiple Enterprise Servers are deployed, at least one must be configured as a Logic Server per pathcode. Additional Enterprise Servers can be added to an Orchestration and they can be deployed after your initial plan is deployed.

3. HTML Servers

   One to many HTML Server instances can be created and each will be associated with one specific pathcode that is available on the Enterprise Server. Additional HTML Servers can be added to an Orchestration and they can be deployed after your initial plan is deployed.

4. AIS Servers

   Zero to many AIS Server instances can be created and each will be associated with a specific HTML Server instance. Additional AIS Server instances can be added on to your plan and deployed after your initial plan is deployed.
   
   Important: If you do not specify at least one AIS Server, the full functionality of certain JD Edwards EnterpriseOne applications will not be available.

   Important: You cannot specify an HTML Server instance to also support an AIS Server. You must create a separate instance for each AIS Server.

5. Deployment Server

   A single Deployment Server can be created and all pathcodes can be selected regardless of pathcodes selected for your runtime servers.

Before orchestrating an Advanced Deployment Plan, the recommended practice is to first orchestrate a Deployment Plan using Quick Start. The Quick Start procedure is documented in the section of this document entitled: Orchestrate Using Quick Start Mode. After this Quick Start orchestration is created, you can use the Advanced mode to modify, delete, or add on additional server instances. Alternately, experienced users can use Advanced Mode to create an orchestration from start , which assumes they are aware of the required sequence of creation and the interdependencies.

Note: For any orchestration created or modified using the Advanced Mode Deployment Plan, you can click the Options function from the menu bar to change your Global Settings or to Reset your settings (that is, to delete your configuration details, global settings, and orchestration data).

To use the JD Edwards Provisioning Console to orchestrate and deploy an Advanced Deployment Plan:

1. On the JD Edwards Provisioning Console, click the Orchestrate icon.



2. On JD Edwards Servers, click on the instance of an existing server, or click the New Server icon to add a new JD Edwards service. Alternately you can select the desired server from Service Types on the left tab, and then click New Server to add a New Server.

 

Note: The remainder of this procedure includes steps to either add (where allowed) or modify (existing) these instances:

• Database Server
• Enterprise Server
• Web Server (for example, HTML Server and AIS Server)
• Deployment Server*
* The Provisioning Console will not allow you to add more than one of these server types because only one server of this type is supported per deployment.

Database Server

The available Database Server Types are: Oracle Databaser Server and Microsoft SQL Server.


You can create five database instances if you select one schema per instance. For example, if you select Development and Shared schemas for an instance, you can create three more database instances. For one deployment instance, you can have a maximum number of five schemas distributed across one or many database instances.

You can provision the Database Server instance with the available schemas as required. The following schemas are available for the database instance:

• Development
• Shared (required)
  
• Prototype
• Production
• Pristine

 

Adding an Oracle Database Server Instance

To add an Oracle Database Server instance:

1. Click the New Server icon and select Database Server from the Select a Server Component window.



2. On Database Server Instance Details, enter the appropriate values for your installation as illustrated in the following example, and then click OK.

 

3. You should now be able to view multiple instances of the Database Server.



4. Click View from the Application Options tab to view the existing configuration for the Database Server. To modify the instance configuration use the Application Options tab and choose the Edit option.

Important: The Provisioning Console for One-Click Provisioning allows you to edit the schemas and demo data settings for an existing Database Server post deployment.



5. To delete the instance, use the Application Options tab to select Delete.
Adding a SQL Server Database Instance

To add a SQL Server Database instance:

1. Click the New Server icon and select Database Server from the Select a Server Component window.



2. On Database Server Instance Details, enter the appropriate values for your installation as illustrated in the following example, and then click OK.

 

3. You should now be able to view multiple instances of the Database Server.



4. Click View from the Application Options tab to view the existing configuration for the Database Server. To modify the instance configuration use the Application Options tab and choose the Edit option.



Important: The Provisioning Console for One-Click Provisioning allows you to edit the schemas and demo data settings for an existing Database Server post deployment.

5. To delete the instance, use the Application Options tab to select Delete.

Enterprise Server

You can define any number of Enterprise Server instances. If you only want one Enterprise Server, you should define it to run both Logic and Batch. If you want to define multiple Enterprise Servers, at least one must be a Logic Server per pathcode.

To add an Enterprise Server:

1. Click the New Server icon and select Enterprise Server from the Select a Component window.



2. On Enterprise Server Instance Details, enter the appropriate values for your installation as illustrated in the following example, and then click OK.



3. You should now be able to view multiple instances of the Enterprise Server.

   

4. If an Enterprise Server exists, click View from the Application Options tab to view the existing configuration for the Enterprise Server. To modify the instance configuration use the action tab and choose the Edit option. Use the Clone option to clone the Enterprise Server instance.



5. To delete the instance, use the Application Action tab to select Delete.

Web Server

The Instance Type for Web Servers can be any of the available servers types selectable from the drop-down list ; however, you must have at least one configured HTML Server saved prior to creating an associated AIS instance.

You can define any number of Web Server instances.

To add or modify a Web Server instance on premises:

1. Select the Service Type for Web Server.
• To create a new Web Server, click the New Server icon and then the Web Server icon and complete the required fields.
• To modify an existing Web Server, click View from the Application Actions tab to view the existing configuration for the Web Server. To modify the instance configuration use the action tab and choose the Edit option.
2. On Web Server Instance Details, enter appropriate values for your installation as illustrated in the following examples for each of these Web Server types:
   
   • HTML Server
   • Application Interface Services (AIS) Server

Important: Because multiple Web Servers instances can run on the same WebLogic Server running on premises, you MUST specify different ports for each instance.





3. Click the OK button.

4. Verify the Web Server instances you modified or added is displayed in the JD Edwards Servers window.

   

5. To delete any web instance, use the Application Actions tab to select Delete.

Deployment Server

You can use only one Deployment Server per deployment. If you attempt to add more than one Deployment Server, the Provisioning Console displays an error.

To modify the Deployment Server instance:

1. On JD Edwards Servers, click the existing Deployment Server instance, click the Applications Options icon, and then click Edit.



2. On JD Edwards Deployment Server, complete these fields as illustrated in the following example, and then click OK.



3. Verify that the Deployment Server instance you modified is displayed in the JD Edwards Servers window.

4. You can choose the Delete option in the action tab to delete the Deployment Server instance. After you delete the existing Deployment Server instance, you can click the New Server icon, and then select Deployment Server from the Select a Component page to add a new Deployment Server instance.

Note: To deploy an orchestration, refer to the section of this guide entitled: Deploy an Orchestration.

You can add additional Web Servers and Enterprise Servers after you complete your Deployment. You cannot add any other server type after the deployment.

To add additional servers post deployment:

1. On JD Edwards One-Click Provisioning Console, click the Orchestrate icon.

2. On JD Edwards Servers, click the New Server icon, and in the Select a Component window, select Web Server.

3. On Web Server Instance Details, enter appropriate values for your installation.

4. Click the OK button. Similarly, you can add new Enterprise Servers.

5. On JD Edwards Servers, click the Back button.

6. On JD Edwards One-Click Provisioning Console, click the Deploy icon.

7. On JD Edwards Deployment window, review the deployment summary. You can verify the newly added servers in the Deployment Details tab.

Note: To deploy an orchestration, refer to the section of this guide entitled: Deploy an Orchestration.

This procedure describes how to deploy an orchestration, whether it is a Quick Start or an Advanced mode Deployment Plan.

1. After you create a Deployment Plan, from the JD Edwards Provisioning Console, click the Deploy icon.



2. To view the Account details and Global Settings Summary, in the Deployment Details tab click the ">" icon for each server in the Deployment Details to see the details of the servers you provisioned.



3. Click the Back button if required to make additional changes to the server instances.

4. To start the deployment, click the Start Deployment button.

5. On Deployment Status, you can see all the instances and task details and their progress. You can also view the log or summary of each of the tasks.

   The time taken to deploy the servers depends on your customization.



6. Click the Back button if you want to go back to the Deployment Summary window.

Adding Additional Pathcodes Post Deployment

You can add additional pathcodes to the Database Server instance after you start your deployment.

To add additional pathcodes:

1. Click the Orchestrate tile on the JD Edwards One-Click Provisioning Console.

2. On JD Edwards Servers, click on Database Server Instances.

3. Select the Database Server instance, and then use the action tab to choose Edit Schema option.



4. On Existing Database Instance Details, select the available pathcodes.

   An error message window appears if you attempt to delete the previously installed schema or the demo data.

5. Click the OK button.

6. Now you can see the Deployment status as MODIFIED.



7. Click the Back button, and then Click Deploy icon to start your modified deployment.

You can use the export and import functions of the JD Edwards Provisioning Console to save an existing configuration (export) and to reuse (import) the saved configuration.

Export a Configuration

To export a configuration:

1. On the JD Edwards Provisioning Console, click the Orchestrate icon.



2. To export an existing orchestration, on an existing Orchestration, from the title bar select Export Orchestration.



3. On the Save As dialog box, choose a path and file name for the exported orchestration.



4. Click the Save button.
   

Note: If you want to view the raw contents of the .json file, you can open the file in an ASCII editor as shown in the following example.

Import an Orchestration

To import an existing exported orchestration:

1. On the JD Edwards Provisioning Console, select the Orchestrate icon.



2. Select the Import icon and follow the prompts to choose the Orchestration Template .json file that was previously exported.

The Deployment Server that is deployed by the Provisioning Server includes all the required third-party products including a JDK, E1Local Oracle database, EnterpriseOne database client, and Visual Studio Runtime libraries for 2010 and 2013. If you will be performing package builds, refer to the subsection entitled: Package Build Considerations.

• Accessing the Deployment Server
• Delete and Recreate System – 920 on SQL Deployment Server
• Delete the ESU.reg File
• Enable Change Assistant Access to the Update Center
• Package Build Considerations

Accessing the Deployment Server

Delete and Recreate System – 920 on SQL Deployment Server

Delete the ESU.reg File

Enable Change Assistant Access to the Update Center

Package Build Considerations

You can use One-Click Provisioning to install a standalone Deployment Server. A Standalone Deployment Server is when you first use One-Click Provisioning to provision a Deployment Server only, and then follow that to provision other servers such as the Database server, Enterprise Server, and HTML Servers. This section describes how to complete post installation steps for such a Standalone Deployment Server.

If you have used One-Click Provisioning to deploy a Standalone Deployment Server (that is, you did not use One-Click to initially deploy a complete system), you must  perform this procedure on your Deployment Server in order to enable access by JD Edwards EnterpriseOne:

• Enable DEP920 Login for an Oracle Database
• Configure the ODBC Data Source for SQL Server to Enable JD Edwards EnterpriseOne to Log Into the Deployment Server

Enable DEP920 Login for an Oracle Database

Important: This section is only applicable if you deployment of JD Edwards EnterpriseOne includes an Oracle Database Server.

After you have used One-Click Provisioning to deploy the complete suite of JD Edwards EnterpriseOne servers, you need to enable EnterpriseOne login to the Oracle database from the Deployment Server.

1. Access the Deployment Server as described in the task in preceding section entitled: Accessing the Deployment Server.
2. Edit the jde.ini file, which is typically located in this directory:
   
   c:\Windows
3. Edit the jde.ini file to provide a valid value for the SecurityServer= setting. This is the machine name for your Enterprise Server. For example:
   
   [SECURITY]
   SecurityServer=oraes
4. Save and close the jde.ini file.
5. Navigate to the location of the Oracle Client that is installed on your Deployment Server. For example:
   
   C:\JDE\oracle1212\product\client_1\network\admin
   
6. In the above directory, edit the tnsnames.ora file to add the listener details. You can copy these details from the tnsnames.ora file on your Server Manager machine or your Enterprise Server machine. This tnsnames.ora file is located in the same location on each machine. From Server Manager, you can use this navigation to find open this tnsnames.ora on either the Server Manager or Enterprise Server machines:
   
   HTML Server > DATABASE > Tnsnames
   
   For example, this is the listener section you should copy:
   
   JDEORCL =
     (DESCRIPTION =
       (ADDRESS = (PROTOCOL = TCP)(HOST = oradb.subnet.vcn.com)(PORT = 1521))
       (CONNECT_DATA =
         (SERVER = DEDICATED)
         (SERVICE_NAME = jdeorcl.subnet.vcn.com)
     )
   )
7. Save and close the tnsnames.ora file.
8. Navigate to the location of the E1Local Network, which is typically:
   
   C:\JDE\DEP\Oracle\E1Local\NETWORK\ADMIN
   
9. In the above directory, edit the tnsnames.ora file to add the same listener details that you obtained and copied in the previous step in this procedure. 
10. Save and close the tnsnames.ora file.
11. Validate the configuration of the tnsnames.ora files by running ActiveConsole.exe and logging into the DEP920 environment.

Configure the ODBC Data Source for SQL Server to Enable JD Edwards EnterpriseOne to Log Into the Deployment Server

Use this procedure to configure the SQL Native Client 11 that was delivered with the deployment of the SQL Server  database on the Deployment Server that was provisioned by One-Click Provisioning. This configuration is necessary to enable JD Edwards EnterpriseOne to log into the Deployment Server.

1. Access the Deployment Server as described in the task in preceding section entitled: Accessing the Deployment Server.
2. Navigate to this directory:
   
   C:\Windows\SysWOW64
   
3. Launch this executable to open the ODBC Data Source Administrator (32-bit) program:
   
   odbcad32.exe
   Upon execution, the following screen is displayed:
   
   

   

4. On ODBC Data Source Administrator (32-bit), click the System DSN tab.
5. Click the Add button.



6. On Create New Data Source, scroll through the list select this option:
   
   SQL Native Client 11
7. Click the Finish button.



8. On Create a New Data Source to SQL Server, complete these fields:
   
   
   • Name
     Enter the value JDE920.
     
   • Description
     Optionally you can enter a description, such as JDE920.
     
   • Which SQL Server do you want to connect to?
     Enter the fully qualified domain name (FQDN) for your SQL Server Database Server.
     
     For example:
     
     windb15.sub0123456789.testdnsvcn.com
9. Click the Next button.



10. On Microsoft SQL Server DSN Configuration, click this radio button:
    
    With SQL Server authentication using a login ID and password entered by the user.
    
11. Complete these fields:
    
    
    • Login ID:
      Enter the value: sa
    • Password:
      Enter the password for your SQL Server database.
12. Click the Next button.
    
    Important: At this point the system validates the connection to the SQL Server database using these credentials. You cannot proceed until the credentials are validated.



13. On the above screen, Microsoft SQL Server DSN Configuration, you should accept the default values without making any changes.



14. On the above screen, Microsoft SQL Server DSN Configuration, again you should accept the default values without making any changes.
15. Click the Next button.



16. On ODBC Microsoft Server Setup, click the Test Data Source button to verify the configuration of the ODBC Data Source for SQL Server is successful.

You must use Server Manager to update the jde.ini file on the Enterprise Server to specify the correct version of Visual Studio.

1. Use Server Manager to open the managed instance of the Enterprise Server that is deployed in Oracle Cloud Infrastructure.
2. Go to Configuration > Advanced Mode.
3. Select the Package Build section.
4. Scroll down to the Visual Studio Compiler Version setting.
5. Select the version of the Visual Studio which you have installed on the target Enterprise machine.
6. Click the Apply button to save the setting.
7. To enable the configuration changes to take affect, stop and start the instance for the updated Enterprise Server.
   

If you want to install a JD Edwards EnterpriseOne Development Client to work with your instance of the JD Edwards EnterpriseOne One-Click Provisioning, you must provision an additional Microsoft Windows machine in your on premises domain. After the Microsoft Windows machine is provisioned, the process to set up and install a Development Client is virtually the same as an on premises Development Client; however, all machines involved are on your on premises domain. Because a Microsoft Windows instance on premises is simply a base OS image, you must also install all required third-party software and build a full client package on the Deployment Server. The Development Client installation is exactly the same as currently documented for traditional On Premises. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for detailed instructions. The preceding link is to the HTML version of the guide, while this link is to the PDF version.

Consider the following requirements before you create the Development Clients:

• Windows machines are on the private network, and that they can communicate with the Database and the Enterprise Servers.
• A full package build is completed on the Deployment server. This package build creates the Development Client package installation. The delivered FA package will technically install a Development Client, but it is does not work for most developer activities.
• Ensure that IPv6 is disabled on the Microsoft Windows machine on which you will install the JD Edwards EnterpriseOne Development Client.
  
  Run this command to disable IPv6:
  
  reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 0xFFFFFFFF
  
  Use ipconfig to verify the status of IPv6 is set to disabled.

For SQL Server installations, you should update the JDE.INI template for any future Development Client installations to reference the correct Bootstrap Data Source.

The JDE.ini template is located in the following directory.

<Deployment server install location> \OneWorld Client Install\Misc

Change the values as highlighted below:

[DB SYSTEM SETTINGS]

Decimal Shift=Y

Version=43

Default User=JDE

Default Role=*ALL

Default Env=DV920

Default PathCode=DV920

Base Datasource=System - 920

Object Owner=SY920

Server=SQLDBNODNS

Database=JDE920

Load Library=

Decimal Shift=Y

Julian Dates=Y

Use Owner=Y

Secured=Y

Type=S

Library List=

Library=

DatabaseName2=JDE920

DatabaseInstance=

ServerPort=1433

JDBNETUse=N

UnicodeFlag=Y

LOBFlag=N

Default Pwd=_

The deployment of JD Edwards EnterpriseOne One-Click Provisioning includes temporary Certificate Authority (CA) certificates. Because these certificates are set to expire at preset and non-extendable times, you must obtain and install your own CA certificates. These must be certificates that are verified by a verified CA authority such as Entrust and Symantec Corporation. The following outlines the general procedure to create a Keystore and to generate a Certificate Signing Request (CSR).

1. In your local environment, obtain and install a Java Keystore. This is a repository for security certificates – either authorization certificates or public key certificates – plus corresponding private keys. These keys are used for SSL encryption by the Oracle WebLogic Server.  A file with extension jks serves as keystore.
2. From the Keystore, generate a Certificate Signing Request (CSR).
3. Export the Certificate Signing Request (CSR).
4. Validate the CSR. For example, you could use the validation tools provided by Symantec (https://ssltools.websecurity.symantec.com/checker).
5. Submit the CSR to the Certificate Authority such as Entrust or Symantec Corporation.
6. Upon return receipt, import the validated certificates to the Keystore for each server. That is, each server that must communicate with another must have its own certificate plus that of the target server. In this case, the HTML Server must have its own certificate plus that of the AIS Server, and vice versa.
7. Logged in as the WebLogic Adminstrator, you must manually modify each of these instance of Oracle WebLogic Server within your One-Click deployment to use the new Keystore:
• Server Manager Console
• Each instance of a JD Edwards EnterpriseOne HTML Server (JAS)
• Each instance of a JD Edwards EnterpriseOne AIS Server
8. You should also modify the parameters using Server Manager to use the https connection for communication between the HTML Server and the AIS Server. 
1. In the HTML instance, modify the following Web Runtime parameters to use https, a fully qualified domain name, and https port:
   
   

   

2. In the AIS instance, modify the following HTML Server parameters to use https, a fully qualified domain name, and https port:
   
   

   

Tip: After you have SSL configured and tested, it is recommended that you disable all the non-SSL ports.

For additional details on working with CA certificates on your Oracle WebLogic Server, refer to this guide: Fusion Middleware Administering Security for Oracle WebLogic Server 12.1.3.

Enabling a Firewall

You must turn off the firewall for each of the Windows-based server in order to use JD Edwards EnterpriseOne One-Click Provisioning. After the provisioning is complete, you can turn the Firewall back on using the following procedure.

1. Ensure that the security port list in your machine is set to allow ports as shown in the following table in the column labelled Ports.
2. For each JD Edwards EnterpriseOne Windows-based server, turn the Firewall back on by following steps:
1. Access the Control Panel.
2. Click System and Security.
3. Turn on Windows Firewall.
3. For each of the JD Edwards EnterpriseOne servers, use the following steps as necessary to specify open ports:
1. Select the Advanced settings and highlight Inbound Rules in the left-side pane.
2. Right-click Inbound Rules option, and then select New Rule.
3. Add the port you need to open and click Next.
4. Add the protocol (TCP or UDP) and the port number=nnnn and click Next. Here, nnnn is the port number that must be open; the numbers are listed in the following table in the column labelled Ports.
5. Select Allow the connection in the next window and click Next.
6. Select the network type as required and click Next.
7. Enter the Name for the newly created rule, and then click Finish.

Component	Machine	Ports	Comment
Server Manager Console	Provisioning Server Machine	8998	https (SSL)
	Provisioning Server Machine	8999	http (non-SSL)
One-Click Provisioning Console	Provisioning Server Machine	3000
Server Manager Console JMX	Provisioning Server Machine	14501
Server Manager Agent JMX	In each machine where these servers are installed: · Database Server · Enterprise Server · WebLogic Server · Deployment	14502-N	N depends on number of instances created under a particular Server Manager Agent.   For example, for two instances under single agent, ports 14502-14503 should be opened.
Oracle Database Server Listen Port	Database Server Machine	1521
SQL Database Server Listen Port	Database Server Machine	*	User specified at the time of installation.
Enterprise Server Listen Port	Enterprise Server Machine	6017
Enterprise Server Predefined Ports	Enterprise Server Machine	6018- 60NN	NN depends on the number of predefined ports, where the default is 6 ports. Therefore, for Release 9.2, if the default values are used, the port range would be 6018-6023. See Enterprise Server Predefined Ports below for further details.
WebLogic Admin Console	WebLogic Server Machine	*	User specified at the time of installation.
		*	User specified at the time of installation.
HTML Server	WebLogic Server Machine	*	User specified using Provisioning Console.
AIS Server	WebLogic server Machine	*	User specified using Provisioning Console.
All Servers	All Servers deployed on Windows	5985	Used for the winrm port for communication between all the Servers.
Remote Desktop Protocol (RDP)	All Servers deployed on Windows	3389
Samba ports	Provisioning Server Machine	139 and 145

* This is a variable value depending on the value entered in the Provisioning Console.

After you enable the firewall, if the runtime metrics and the health check do not work as expected, find out the  ports used for embedded agent. Use the following procedure to access the port details:

1. Enable the embedded agent logging by adding the following entries in the $SCFHA\config\agent.properties file.

   log.level=ALL

   log.embedded.instances=true

2. The embedded agent logs are added in the  $SCFHA\logs directory. The log files are named as <managed_instance>.log.
3. Restart the managed instance.
4. The port number used for the embedded agent is displayed in these log files. Add firewall inbound rules for the ports in the log file.

After the Provisioning Console has successfully completed deploying all servers defined in the Orchestration function of plan creation, you can access these deployed JD Edwards EnterpriseOne servers and Development Client using their Public IP Address:

• Server Manager Console
• HTML Server
• AIS Server
• Deployment Server

After the Server Manager Console is started, you can access it using its host name using this syntax:

http://<Host Name>:8999/manage

For example:

http://abc.pqr.xyz:8999/manage

Important: You should always use HTTP to access the Server Manager Console for normal operations. Although the Server Manager Console is also enabled for HTTPS/SSL protocol, such access is restricted for internal use as part of the REST/API functionality, and should not be used for normal operations.

After your HTML Server is deployed, you can access it using its host name using this syntax:

https://<Host Name>:<port as defined in orchestration>/jde/E1Menu.maf

Important: The file name E1Menu.maf is case-sensitive and must be specified exactly as shown here.

For example:

https://abc.pqr.xyz:8001/jde/E1Menu.maf

After your AIS Server is deployed, you can access it using its host name using this syntax:

https://<Host Name >:<port as defined in orchestration>/jderest/defaultconfig

For example:

https://abc.pqr.xyz:8002/jderest/defaultconfig

You can access your Deployment Server using Microsoft Windows Remote Desktop Protocol (RDP). To do so, provide the host name which you have given during the provisioning. On that tab, locate the instance name that you gave for your Deployment Server. 

The following table lists suggested troubleshooting topics and resolutions. Additionally there may be code or documentation bugs created within the Oracle BUG system.

• One-Click Provisioning Console Troubleshooting Tips
• Enterprise Server Provisioning Fails - Communication Failure
• Enterprise Server Provisioning Fails - Health Check Fails
• Enterprise Server Not Able to Run PORTTEST Manually
• HTML Server Intermittently Unavailable
• Server Manager Console Fails to View Log File and Download Log for Enterprise Server and HTML Server
• PDB on Compute Not Open
• Not Able to View and Download Server Manager Home Logs When Server Manager is SSL-Enabled
• The JD Edwards EnterpriseOne HTML Server Login Fails
• The JD Edwards Enterprise Server - Port Test Fails
• Resolving host name Issues During Provisioning
• Health Checks Fail as Final Step in OCI Provisioning
• Security Server JdeSocket Or SocketException Errors When Logging Into EnterpriseOne
• Invalid Identifier for Table F980051

One-Click Provisioning Console Troubleshooting Tips

This section contains the following troubleshooting tips for the EnterpriseOne One-Click Provisioning Console:

• Accessing a Previously Saved Provisioning Console Configuration
• Console Administration
• Console Service Status
• Start the Console
• Stop the Console
• View the Console Logs
  

Accessing a Previously Saved Provisioning Console Configuration

Symptom:	You cannot access a previously created Quick Start Deployment Plan.
Cause:	After you created a Quick Start Deployment Plan (either complete or partial), you exited the browser used to connect to the One-Click Provisioning Console.
Resolution:	When you next access the Provisioning Console, you will be prompted to enter the same credentials that you entered for the first access to the console. Those credentials are the password for the Server Manager for JD Edwards EnterpriseOne. After the credentials are validated, you can access the previously saved configuration.

Console Administration

The One-Click Provisioning Console process is configured as a systemd service in the One-Click Provisioning Server image. The configuration file (E1CloudConsole.service) is located in this directory:

C:\JDE\bin\E1CloudConsoleWin.ps1

Console Service Status

Access the Task Manager and verify that the node.exe is running in the Provisioning Server machine:

Start the Console

Run the following command in the power shell to start the One-Click Provisioning Console service.

PS C:\JDE> E1CloudConsoleWin.ps1

Outside the machine, you can access the One-Click Provisioning Console application using the below URL:

https://<#PUBLIC_IP#>:3000/

Stop the Console

Access the Task Manager and kill the node.exe process if it is running in the Provisioning Server machine.

View the Console Logs

See the following One-Click Provisioning Console log files in C:\JDE\PP\E1CloudConsole\logs:

• E1ProvisionConsole.err
• E1ProvisionConsole.out

The input validation logs files are located in this path: C:\JDE\PP\E1ProvisionPrime\InputValidation\log

Press Page-Down to scroll through the logs.

Enter Shift + G to scroll to end of the log.

Note: The One-Click Provisioning Console logs are completely regenerated each time the Console is run.

Enterprise Server Provisioning Fails - Communication Failure

Symptom:	Provisioning fails to deploy the Enterprise Server with an error returned indicating a communication failure.
Cause:	A timeout may have occurred during communications between the One-Click Provisioning processes and the on premises machine.
Resolution:	Restart the deployment of One-Click Provisioning.

Enterprise Server Provisioning Fails - Health Check Fails

Symptom:	Porttest remotely executes, but fails
Cause:	Possibly a timing issue if the kernels are not starting up fast enough to execute a porttest successfully.
Resolution:	Rerun the Deployment again. It should quickly skip to the Ent Health Check and pass.

Enterprise Server Not Able to Run PORTTEST Manually

Symptom:	Not able to run PORTTEST manually on a Microsoft Windows Enterprise Server.
Cause:	The Service user for the Enterprise Server is not set to opc.
Resolution:	You must the Windows Service user on the Enterprise Server Service User to opc using this   documented procedure:   JD Edwards EnterpriseOne Administration Guide     - 4. Administering the Windows Server       - 4,3 Working with Network Services        - 4..3.2 Setting Up the Network Service https://docs.oracle.com/cd/E53430_01/EOTSW/windows_server.htm#EOTSW00222

HTML Server Intermittently Unavailable

Symptom:	There is an intermittently occurring issue with the HTML server provisioned on the WebLogic Server going down and users not being able to access the EnterpriseOne HTML login page. Generally when this issue occurs, the below error is displayed in the WebLogic Server logs or in the HTML Server logs: java.lang.OutOfMemoryError: PermGen space
Resolution:	To bring up the EnterpriseOne HTML server when it goes down the with above error, try one of the following steps: Restart the EnterpriseOne HTML Server instance from the Server Manager Console and then check if the EnterpriseOne HTML login page is accessible. If the JD Edwards EnterpriseOne HTML Server login page is not accessible even after restart, then set the below JVM arguments in the HTML Server from the WebLogic Server console and then restart the HTML Server. Log in to the WebLogic Server console. Go to the Servers on the environment tab and then select the HTML Server. Go to Server Start tab and click the Lock & Edit button in the left upper corner. In the Arguments section, change the values for the following arguments from their existing value to 1024m: -XX:PermSize=1024m -XX:MaxPermSize=1024m In the Arguments section, go to the end and enter one line space and paste the below arguments: -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -XX:+UseConcMarkSweepGC Click the Save button. Click the Activate Changes button in the left upper corner. Restart the EnterpriseOne HTML Server. If the JD Edwards EnterpriseOne HTML Server login page is still not accessible then, free up some resources (OCPU and memory) from the cloud domain and restart the EnterpriseOne HTML Server from the Server Manager console.

Server Manager Console Fails to View Log File and Download Log for Enterprise Server and HTML Server

Symptom:	Server Manager Console Fails to View Log File and Download Log for Enterprise Server and HTML Server.
Resolution:	You should always use the HTTP to access the Server Manager Console for normal operations. Although the Server Manager Console is also enabled for HTTPS/SSL protocol, such access is restricted for internal use as part of the REST/API functionality, and should not be used for normal operations.

PDB on Compute Not Open

The Console checks to ensure the Pluggable Database (PDB)  on premises is open (set to READ WRITE) as you begin to provision it. If the PDB is not open, the Console scripts will issue commands to open it. However, if the PDB is still closed (not set to READ WRITE) when the deployment commences, the deployment will fail. Use the following procedure to determine if the PDB is open, and if not how to set it to open.

1. Connect to the database using this command:
   

   sqlplus '/as sysdba';

2. Verify the pluggable database JDEORCL is open using this command:

   select OPEN_MODE from v$pdbs where NAME = 'JDEORCL';

3. If the OPEN_MODE is set to READ WRITE, then the PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.
4. If the OPEN_MODE is not READ WRITE, then the PDB is not open. Open the PDB using this command:

   alter pluggable database JDEORCL open;

Not Able to View and Download Server Manager Home Logs When Server Manager is SSL-Enabled

When Server Manager is SSL-enabled, the users may not be able to view and download the Server Manager Home logs. The root cause may be because the proper security certificates are not available. For instructions on how create and import security certificates, refer to these documents:

• JD Edwards EnterpriseOne Tools Server Manager Guide

• JD Edwards EnterpriseOne Tools Security Administration Guide

The JD Edwards EnterpriseOne HTML Server Login Fails

If the JD Edwards EnterpriseOne HTML Server login fails, run the port test on the JD Edwards EnterpriseOne Enterprise Server. If the port test fails, check the host entries in the /etc/hosts file. See Edit the /etc/hosts File for Connectivity section in Preparing for a Deployment of JD Edwards EnterpriseOne On Premises on Microsoft Windows.

The JD Edwards Enterprise Server - Port Test Fails

If the port test fails on the JD Edwards EnterpriseOne Enterprise Server, check the host entries in the /etc/hosts file. See Edit the /etc/hosts File for Connectivity section in Preparing for a Deployment of JD Edwards EnterpriseOne On Premises on Microsoft Windows.

Resolving Host Name Issues During Provisioning

If you encounter host name issues during orchestration because the provisioning was run against machines with the long host names, FQDNs, or both, then use the following procedure to resolve the issue:

1. On the operating system level, change the host names of all servers in the on premises architecture to use a short host name without the FQDN.
2. On the database level, change all the host names in JDE tables to use short host names without using the FQDN.
3. Ping all the machines with short host names and verify that the ping test is successful.

See Understanding Machine Names for more information.

Health Checks Fail as Final Step in OCI Provisioning

If the health checks fail during the final step in OCI Provisioning (as shown in the example below), it is likely because the predefined ports for the Enterprise Server are either not enabled or not properly defined in the VCN. For details on enabling this setting, refer to the section of this document entitled: Enterprise Server Predefined Ports.

Security Server JdeSocket Or SocketException Errors When Logging In To EnterpriseOne

If a JD Edwards EnterpriseOne Server is deployed inside a firewall-protected network, you must enable predefined ports so that all NET server ports are allocated within the predefined port range. For details on enabling this setting, refer to the section of this document entitled: Enterprise Server Predefined Ports.

Error ORA-00904: "NRUSER1": Invalid Identifier for Table F980051

The JAS log files displays the following error after you install EnterpriseOne using the JD Edwards One-Click Provisioning Console with Tools 9.2.2.4:

[SEVERE] - [JDBJ] SQLException occured in the SQLPhysicalConnection.select():Auto: | Table or View Name = F980051 - Data Source[0] = System - 920 java.sql.SQLSyntaxErrorException: ORA-00904: "NRUSER1": invalid identifier

[SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: ORA-00904: "NRUSER1": invalid identifier . java.sql.SQLSyntaxErrorException: ORA-00904: "NRUSER1": invalid identifier

[SEVERE] - [BASE] com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: ORA-00904: "NRUSER1": invalid identifier . com.jdedwards.database.base.JDBException: [SQL_EXCEPTION_OCCURRED] An SQL exception occurred: ORA-00904: "NRUSER1": invalid identifier

Cause:

The delivered image for One-Click Provisioning has incorrect OCM mappings for the F980051 table. The OCM for this table is pointing to the System - 920 database data source where the structure of the table is not consistent with the table specs.

Solution:

1. Check both the System and the Server Map data source OCM mappings and change the OCM mappings as shown in the following list:
   Use the following correct OCM mappings for F98005* tables:
• F980051 (Bell Status) mapped to Control Tables - <Environment>
• F980052 (Notification Execution History) mapped to Control Tables - <Environment>
• F980053 (Subscription Metadata) mapped to Control Tables - <Environment>
• F980054 (Notification Queue) mapped to System - 920
• F980055 (Notifications Constants) mapped to System - 920
• F980056 (Notifications Offline Repository) mapped to System - 920
• F980057 (Notifications Offline Repository Archive) mapped to System – 920
2. Restart the Enterprise service.

For more information, see Doc ID 2408472.1

Refer to the companion Oracle by Example (OBE) document entitled: Preparing for a Deployment of JD Edwards EnterpriseOne On Premises on Microsoft Windows. This document describes these tasks:

• Set Preferences to Allow the Installation of Linux Servers
• Create a Pre-Install Worksheet
• Obtain the Images for JD Edwards from the Oracle Marketplace
• Create a Storage Volume for the One-Click Provisioning Server
• Generate Secure SHell (SSH) Key Pairs on Your Local System
• Upload the SSH Private Key to the on premises machine
• Reserve a Public IP Address for the One-Click Provisioning Server Image
• Download the JD Edwards EnterpriseOne VM Configuration Tool from the Oracle Software Delivery Cloud
• Use the VM Configuration Tool to Generate the Security Orchestration for the One-Click Provisioning Server
• Upload and Run the Security Orchestration for Cloud
• Create an Instance for the One-Click Provisioning Server

Refer to the companion tutorial entitled: Deploying JD Edwards EnterpriseOne On Premises on Windows.
In this tutorial, you will learn how to:

• Configure Your Server Manager Account
• Create and Deploy a Quick Start Deployment Plan
• Create and Deploy an Advanced Deployment Plan

Refer to the companion Oracle by Example (OBE) document entitled: Administering Your Deployment of JD Edwards One-Click Deployment. This document provides information on these topics:

• List of Open Ports and Protocols in Security List for Provisioning JD Edwards EnterpriseOne Servers in the on premises machine
• Start or Stop Services Configure Public IP Address/Internal host name on Client Machine
• About JD Edwards EnterpriseOne Security
• Access the Oracle Traffic Director (OTD)
• Using the Linux Logical Volume Manager (LVM) to Manage Free Disk Space on an on premises instance

Server Manager for JD Edwards EnterpriseOne is a web based application used to manage the complete life cycle of the JD Edwards EnterpriseOne server products. Refer to the JD Edwards EnterpriseOne Tools Server Manager Guide.

The JD Edwards EnterpriseOne Tools Security Administration Guide contains comprehensive instructions and recommendations for setting up a secure EnterpriseOne environment. It contains pre- and post-installation security considerations, as well as instructions on how to use EnterpriseOne security applications to ensure only authorized individuals have access to EnterpriseOne applications, features, and data. This guide also contains instructions on using security certificates.

Refer to the JD Edwards EnterpriseOne Applications Release 9.2 Installation Guide for Oracle on UNIX for more information on these topics:

• Working with Installation Planner for an Install
• Working With Installation Workbench
• Copying an Environment to Another Environment
• Adding a Server to an Existing Configuration
• Understanding JD Edwards Environments and their Relationship with the Database

Users have the option to load their own data onto the Deployment Server for subsequent use by the environment created by the JD Edwards EnterpriseOne One-Click Provisioning Server. The tutorial describing this functionality is entitled: Migrating to a JD Edwards EnterpriseOne Multi Tier Deployment on Oracle Compute Cloud Service Instance.

Refer to these resources:

• Working with the JD Edwards One-Click Provisioning Console Video Tutorial

For additional information on how REST APIs are used with JD Edwards EnterpriseOne One-Click Provisioning, refer to the JD Edwards EnterpriseOne Tools REST API for Server Manager. Further information on using REST APIs is available for customers with an Oracle customer ID in this document on My Oracle Support: E1: SVM: How To Test Server Manager REST API With Tools Release 9.2.1.0 and newer (Doc ID 2222019.1).

Refer to Upgrading JD Edwards EnterpriseOne to Release 9.2 using One-Click Provisioned Target Environment for more information on these topics:

Execute the JDE Simplified Upgrade Utility

Using the Simplified Upgrade Process